-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data persistence in candidate views #2613
Conversation
Visit the preview URL for this PR (updated for commit dd8d9d9): https://jac-admin-develop--pr2613-bugfix-candidate-det-uncycwwu.web.app (expires Sat, 28 Dec 2024 10:37:58 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 4e92cf51659207b0ae3509dc5c40edde50edfec0 |
Visit the preview URL for this PR (updated for commit 5522b6c): https://jac-apply-admin-production--pr2613-bugfix-candidate-de-9m629uc9.web.app (expires Wed, 25 Dec 2024 15:19:47 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 2f31b7832d58b04f07d3816f45a5d09d461ded5e |
@tomlovesgithub can you make the testing instructions a bit clearer then I'll test it and code review it? cheers |
What's included?
Details in the candidate view, (Character Information, Equality and Diversity) were getting stuck when looking through different individuals, in circumstances when there were no answers.
(ie. candidate A has answers for Char Info and E&D survey, Candidate B has none, Navigating to candidate A, then to Candidate B, you see candidate A's answers for Char Info and E&D).
Who should test?
✅ Product owner
✅ Developers
✅ UTG
How to test?
Ensure no answers persist when looking through different candidates.
Risk - how likely is this to impact other areas?
🟢 No risk - this is a self-contained piece of work
PREVIEW:DEVELOP
can be OFF, DEVELOP or STAGING